Managing Jobs
This section explains how job processing is managed with Bentley OpenUtilities Designer Server.
Changing the Status of Jobs
The Status column of the Job Activity Grid (Fig. 0-28) indicates the current status of the job. A job can have one of the following Status categories: Running, Queued, Suspended, Failed, or Canceled.
The status of jobs with the Queued or Suspended status can be changed with the Cancel, Suspend, or Resume commands. The status of a job that is already running cannot be changed. If a job acquires the Failed or Canceled status, it is removed from the Job Activity Grid and transferred to the Server Log Grid.
The Cancel, Suspend, and Resume commands are accessed from the shortcut menu (Fig. 0-29). The Cancel command is also available on the Actions menu and the Standard toolbar.
Canceling Jobs
If you want to cancel a job, its current status must be either Queued or Suspended. The Cancel operation cancels the selected job, removes it from the Job Activity Grid, and adds it to the Server Log Grid.
To cancel a job:
Suspending Jobs
The Suspend operation is available for jobs with the Queued status. When a job is suspended, it stays in the system but will not be run until its status is changed back to Queued using the Resume command. Suspending a job is an event that will cause the job to be displayed in the Server Log Grid, along with details of the status change.
To suspend a job:
Re-queuing Suspended Jobs
A suspended job can be returned to the server queue by changing its status from Suspended to Queued using the Resume command. The Resume action is an event that will be cause the job to be displayed in the Server Log Grid, along with details of the status change.
To re-queue a suspended job:
Changing the Priority of Jobs
By default, Bentley OpenUtilities Designer Server assigns a job a level of priority based on the priority assigned to its job type (see Default Priority). The current priority of a job is displayed in the Priority column of the Job Activity Grid.
You can change a job’s priority as long as the job is still queued and not yet running. There are three default priority levels: Very High, High, Medium, and Low. A change in the Priority setting is an event that will cause the job to be displayed in the Server Log Grid, along with details of the change.
A job’s priority can be changed with the Set Priority command, which is accessed from the Actions menu or the shortcut menu. Job priority can also be changed with the Priority button on the Standard toolbar.
To change the priority of a job:
- In the Job Activity Grid, select the job whose Priority setting you want to change.
- On the Actions menu, point to Set Priority, and then choose the priority level that you want to assign to the selected item(s). Or right-click the selected item(s), point to Set Priority on the shortcut menu, and then choose the new priority level. Or click the arrow on the Priority button on the Standard toolbar and choose the new priority level from the drop-down list.